Re: error message "column "oid" doesn"t exist"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C730F4.25A284E2
Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01C730F4.25A284E2"


------_=_NextPart_002_01C730F4.25A284E2
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The method is updating tables from another source, and filtering the =
dataset to determine whether or not the record already exists. It's =
been adapted from code that was just hitting an MS Access DB, and based =
on the responses I've been getting I'll probably have to go in and =
modify the method to use SQL update statements or batch updating instead =
of the ADO Recordset.Update() method.=20
=20
Your mention of client side recordsets, reminded me of issues with the =
ODBC driver and "dynamic" updating in other places. I was able to get =
around that by converting to client side recordsets and batch updating.
=20
Thanks to everyone who's offered information.
Erika
=20

________________________________

From: greg.campbell@us.michelin.com =
[mailto:greg.campbell@us.michelin.com]=20
Sent: Friday, January 05, 2007 11:11 AM
To: pgsql-odbc@postgresql.org; Erika Marlow
Subject: Re: [ODBC] error message "column "oid" doesn't exist"



You say the problem is happening when you are using VB with ADO and you =
say that is happening at SELECT statements.=20

SELECT statements can generally be read only and so do not need to =
uniquely identify records. Uniquely identifying records and determining =
whether or not they have been updated by someone else comes into play =
for data manipulation statements. This means update DML statements use =
Primary Keys, OIDs, and possibly virtually unique keys (WHERE =
field1=3D'old_value1' and field2=3D'old_value2'). You could see a lot of =
these syntax if logging is turned on.=20

I digress.=20
Do you have a client side cursor and a read only statement? eg.=20

sql =3D "SELECT * FROM some_table"=20
set rs =3D new ADODB.Recordset=20
rs.CursorLocation =3D adUseClient=20
rs.Open sql, myConn, adOpenStatic, adLockReadOnly, adCmdText=20

The MSDN has all the docs on making ADO behave properly as a =
disconnected recordset,=20



Greg Campbell ENG-ASE/Michelin US5
Lexington, South Carolina
803-951-5561, x75561
Fax: 803-951-5531
greg.campbell@us.michelin.com




"Erika Marlow" =20
Sent by: pgsql-odbc-owner@postgresql.org=20

01/05/2007 10:05=20

To
=20
cc
Subject
Re: [ODBC] error message "column "oid" doesn't exist"

=09




Hmm. Well, I am opening the tables for editing. All of the tables have =
unique primary keys that can be referenced. Is there a flag or something =
I can set to prevent it from looking for oid?=20
=20
Thanks,=20
Erika=20


________________________________

From: Oberle, Martin [mailto:martin.oberle@winntec.de]=20
Sent: Wednesday, January 03, 2007 1:36 PM
To: Erika Marlow
Subject: AW: [ODBC] error message "column "oid" doesn't exist"

As far as I know the odbc driver uses the oid to identify the records =
when updating records.=20
The driver adds the column oid to the query when the driver thinks that =
records mjight be updated=20
in the future. The error should not occure whe you open the table =
"readonly".=20
=20
good luck=20
=20
martin=20
=20
-----Ursprüngliche Nachricht-----
Von: pgsql-odbc-owner@postgresql.org =
[mailto:pgsql-odbc-owner@postgresql.org]Im Auftrag von Erika Marlow
Gesendet: Dienstag, 2. Januar 2007 19:00
An: pgsql-odbc@postgresql.org
Betreff: Re: [ODBC] error message "column "oid" doesn't exist"

We are recieving the error message "column "oid" doesn't exist" from a =
series of ODBC calls via ADO in a Visual Basic application. The SQL =
statements are all "SELECT * FROM